<subtitle>National Geographic Topo Waypoint format.</subtitle>
</sectioninfo>
<title>TPG</title>
- <para>National Geographic Topo! Waypoint Format. This filter
+ <para>National Geographic Topo! Waypoint and Route Format. This module
reads and writes .TPG files created by various editions of NG Topo!
-This filter will *not* work with the newer combined .TPO files.
+Reading/writing of route data is not supported yet. This filter will *not* work with the newer combined .TPO files.
Contributed by Alex Mottram.</para>
<para>The option 'datum="datum name"' can be used to override
the default of NAD27 ("N. America 1927 mean") which is correct for the
Hawaiian_mean"</para>
<para>Contributed by Alex Mottram.</para>
</section>
+ <section id="tpo">
+ <sectioninfo>
+ <subtitle>National Geographic Topo! Track Format.</subtitle>
+ </sectioninfo>
+ <title>TPO</title>
+ <para>This module reads and writes
+ .TPO files created by various editions of NG Topo! version 2.7.7 or
+ earlier. This format will *not* work with the newer .TPO files
+ (version 3.0 and later) that have the TPG data combined into them.</para>
+ <para>When writing TPO files, note that every TOPO! state edition
+ employs a slightly different data format, so you will need to
+ specify which state edition to generate output for. The current
+ supported states are CA, NY, NJ, MA, CT, RI, NH, VT, ME. It's
+ fairly easy to add support for additional states. Instructions are
+ in the source code.</para>
+ <para> Additional Options: </para>
+ <para>
+ <option>dumpheader</option> (0/1) Display the file header bytes (useful when adding support for a new state)
+ </para>
+ <para>
+ <option>state</option> State map format to write, default=CA.
+ </para>
+ <para>Contributed by Steve Chamberlin.</para>
+
+ </section>
<section id="unicsv">
<sectioninfo>
<subtitle>Universal csv with field structure in first line.</subtitle>
${PNAME} -i tpg -f reference/tpg.tpg -o mxf -F ${TMPDIR}/topo.mxf
compare ${TMPDIR}/tpg.mxf ${TMPDIR}/topo.mxf
+# TPO (NG Topo!) file format
+# This is hard to test as the datum conversions create minute
+# inconsistencies in the coordinates. We have four reference files:
+# sample1.tpo, sample1.gpx, sample2.gpx, and sample2.tpo. These are
+# used to check the conversion to/from TPO format.
+rm -f ${TMPDIR}/sample1.gpx ${TMPDIR}/sample2.tpo
+${PNAME} -t -i tpo -f reference/track/sample1.tpo -o gpx -F ${TMPDIR}/sample1.gpx
+compare ${TMPDIR}/sample1.gpx reference/track/sample1.gpx
+${PNAME} -t -i gpx -f reference/track/sample2.gpx -o tpo -F ${TMPDIR}/sample2.tpo
+bincompare ${TMPDIR}/sample2.tpo reference/track/sample2.tpo
+
# OZI (OziExplorer 1.1) file format
rm -f ${TMPDIR}/oz.wpt ${TMPDIR}/ozi.wpt
${PNAME} -i ozi -f reference/ozi.wpt -o ozi -F ${TMPDIR}/oz.wpt